System and method for agnostic zero touch provisioning of customer premises equipment

ABSTRACT

A method for zero-touch provisioning is disclosed. The method includes receiving a customer specification of network requirements exclusively specified for a CPE assigned to a specific customer at a specific customer premises. The CSNR includes information describing the premises and information describing an intended operation of the CPE. The method also includes storing a job assignment including a unique CPE identity and service information for the provisioning of the CPE. The identity is linked to the customer through the job assignment. The method also includes provisioning a class of service template exclusively for providing the intended operation of the CPE at the customer premises and paired with the CPE identity through the job assignment. The method also includes receiving a provisioning request sent by the CPE to a FQDN pointed at the ZTP server and including the CPE identity. Finally, the method includes pushing the COS template to the CPE.

RELATED APPLICATIONS

This application is a continuation-in-part of, and claims the benefit ofU.S. Patent Application No. 62/141,852, filed Sep. 25, 2018 titled“Automatic Provisioning of Customer Premises Equipment”, which is acontinuation of, and claims the benefit of U.S. patent application Ser.No. 15/222,198 filed Jul. 28, 2016 titled “Automatic Provisioning ofCustomer Premises Equipment”. The entirety of the above referenceddisclosures is hereby incorporated herein by this reference.

TECHNICAL FIELD

Aspects of this document relate generally to automatically provisioningcustomer premises equipment (CPE).

BACKGROUND

Services such as voice, data, streaming video and other services areoften provided to home and business customers/subscribers by telecomservice providers, multichannel video programming distributors (MVPD)and so on. Customer premises equipment (CPE) may include various typesof terminal equipment to process received MVPD signals to thereby enablesubscribers to view, record, and interact with the services. Among themore common consumer electronics devices are television sets, set-topboxes, cable modems and personal video recorders. The CPE cooperateswith an access network of the service provider to receive appropriateservices thereby.

Traditionally, setting up CPE for customer involves a technicianinstalling the CPE at the customer location, provisioning the CPEdirectly or by cooperating with service provider personnel at a servicenetwork management location, and testing the CPE to ensure that it worksfor its intended purpose, such as a set-top box (STB) and modem forcustomer receiving television, telecom and data services at home. Thetraditional CPE provisioning process is therefore time-consuming andexpensive.

Automatic provisioning of CPE is desired to streamline the CPEprovisioning process and reduce costs. Existing automatic provisioningtechniques are based upon techniques developed for use in provisioningover telephones within the context of a 3G/4G mobile networkenvironment.

However, the 3G/4G network environment for provisioning mobiletelephones is the same everywhere in the mobile network, whereas theservice provider network environment for provisioning a CPE is not onlysubject to significant differences depending upon location, there arealso many more parameters to provision relevant CPE in such a network.That is, automatic provisioning of CPE within a service provider networkrequires the provisioning of many operating parameters, provisioning ofoperating parameters of enormous complexity as compared to mobiletelephones, and the provisioning of these parameters within the contextof local network conditions which may vary considerably and unexpectedlybetween locales.

Conventional methods for provisioning CPE units are often expensive andslow. In an ideal scenario, a customer may be requesting theprovisioning of new services using new CPE units sourced from thenetwork service provider. The network service provider will have apreferred set of equipment that their field technicians and back officepersonnel are adept at installing and configuring. However, even in sucha scenario, the customer must wait for, and pay for, one or more fieldtechnicians to be on-site to begin a multi-step provisioning process foreach CPE unit.

However, in many cases, the circumstances of provisioning new ormodified network services are less than ideal for the network serviceprovider. For example, many customers have invested in a collection ofCPE units, and do not want the expense of replacing all of those unitswith hardware that is preferred by a new service provider. As aconsequence, sometimes the service provider's field technicians aretasked with provisioning CPE units that they are unfamiliar with,requiring the assistance of install personnel from the original CPEvendor, further increasing cost and the length of the install.

SUMMARY

According to one aspect, a method for zero touch provisioning, performedby a zero touch provisioning (ZTP) server in a network, includesreceiving a customer specification of network requirements (CSNR)exclusively specified for a customer premises equipment (CPE) belongingto a device family and assigned to a specific customer at a specificcustomer premises. The CSNR is received prior to the CPE being pluggedinto a network link at the specific customer premises for a first timeand includes information describing the specific customer premises andinformation describing an intended operation to be provided by the CPEfor the specific customer. The CPE having been preconfigured to send aprovisioning request to a fully qualified domain names (FQDN) unique tothe device family and pointed at an IP address of the ZTP server. Theprovisioning request is sent in response to the CPE being plugged intothe network link at the specific customer premises for the first time.CPEs belonging to the same device family are configurable using a shareddevice profile. The method also includes storing, prior to receiving theprovisioning request from the CPE, a job assignment including anidentity that is unique to the CPE and service information for the zerotouch provisioning of the intended operation of the CPE based on theCSNR. The identity is linked to the specific customer through the jobassignment. The method further includes provisioning a class of service(COS) template by selecting and populating at least one device profiledefined for the device family with the service information of the jobassignment, the COS template exclusively created for providing theintended operation of the CPE at the specific customer premises andpaired with the identity of the CPE through at least the job assignment.The method also includes receiving, from the CPE, the provisioningrequest sent by the CPE to the FQDN in response to the CPE being pluggedinto the network link for the first time. The provisioning requestincludes the identity of the CPE. Finally, the method includes pushing,to the CPE, the COS template provisioned using the job assignmentmatching the identity of the CPE, to configure the CPE for performingthe intended operation. The device family is one of a CPE manufacturerand a CPE model.

Particular embodiments may comprise one or more of the followingfeatures. The COS template may be provisioned after the provisioningrequest is received from the CPE. The service information may includeinformation related to service attributes of at least one of apoint-to-point protocol (PPP), local area network (LAN) data, a qualityof service (QoS), dynamic host configuration protocol (DHCP), virtuallocal area network (VLAN), virtual private network (VPN) data,transmission system 1 (T1), primary rate interface (PRI) data, SIPtrunking, SIP proxy server requests, and multiprotocol label switching(MPLS).

According to another aspect of the disclosure, a system for zero touchprovisioning includes a customer premises equipment (CPE) assigned to aspecific customer at a specific customer premises, the CPE belonging toa device family. The CPE is communicatively coupled to a network througha network link at the specific customer premises. CPEs belonging to thesame device family are configurable using a shared device profile. Thesystem also includes a zero touch provisioning (ZTP) server having aprocessor and a memory. The ZTP server is configured to receive acustomer specification of network requirements (CSNR) exclusivelyspecified for the CPE. The CSNR includes information describing thespecific customer premises and information describing an intendedoperation to be provided by the CPE for the specific customer. Theserver is also configured to store a job assignment including anidentity that is unique to the CPE and service information for the zerotouch provisioning of the intended operation of the CPE based on theCSNR. The identity is linked to the specific customer through the jobassignment. The server is configured to provision a class of service(COS) template using information originating from the CSNR by selectingand populating at least one device profile defined for the device familywith the service information of the job assignment. The COS template isexclusively created for providing the intended operation of the CPE atthe specific customer premises and paired with the identity of the CPEthrough at least the job assignment. The server is further configured toreceive, from the CPE, a provisioning request sent by the CPE from thenetwork link at the specific customer premises to a fully qualifieddomain name (FQDN) unique to the device family and resolving to an IPaddress of the ZTP server. The provisioning request includes theidentity of the CPE. The CSNR is received and the job assignment isstored before the provisioning request is received. Finally, the serveris configured to push, to the CPE over the network, the COS templateunique to the job assignment matching the identity received in theprovisioning request, to configure the CPE for performing the intendedoperation.

Particular embodiments may comprise one or more of the followingfeatures. The device family may be one of a CPE manufacturer and a CPEmodel. The CPE may be preconfigured to send the provisioning request tothe FQDN in response to the CPE being plugged into the network link atthe specific customer premises for a first time. The ZTP server may befurther configured to determine the device family of the CPE using theprovisioning request received from the CPE. The ZTP server may befurther configured to determine the device family of the CPE byidentifying the FQDN through which the ZTP server receives theprovisioning request. The ZTP server may be further configured todetermine the device family of the CPE using one of a serial number anda MAC address received in the provisioning request and resolvable to atleast the device family of the CPE. The COS template may be provisionedafter the provisioning request is received from the CPE. The serviceinformation may include information related to service attributes of atleast one of a point-to-point protocol (PPP), local area network (LAN)data, a quality of service (QoS), dynamic host configuration protocol(DHCP), virtual local area network (VLAN), virtual private network (VPN)data, transmission system 1 (T1), primary rate interface (PRI) data, SIPtrunking, SIP proxy server requests, and multiprotocol label switching(MPLS).

According to yet another aspect of the disclosure, a method for zerotouch provisioning, performed by a zero touch provisioning (ZTP) serverin a network, includes receiving a customer specification of networkrequirements (CSNR) exclusively specified for a customer premisesequipment (CPE) assigned to a specific customer at a specific customerpremises, the CSNR received prior to the receipt of a provisioningsignal from the CPE from a network link at the specific customerpremises. The CSNR includes information describing the specific customerpremises and information describing an intended operation to be providedby the CPE for the specific customer. The method also includes storing,prior to receiving the provisioning request from the CPE, a jobassignment including an identity that is unique to the CPE and serviceinformation for the zero touch provisioning of the intended operation ofthe CPE based on the CSNR, the identity being linked to the specificcustomer through the job assignment. The method further includesprovisioning a class of service (COS) template using informationoriginating from the CSNR, the COS template exclusively created forproviding the intended operation of the CPE at the specific customerpremises and paired with the identity of the CPE through at least thejob assignment. The method includes receiving, from the CPE, theprovisioning request sent by the CPE from the network link at thespecific customer premises to a fully qualified domain names (FQDN)pointed at an IP address of the ZTP server. The provisioning requestincludes the identity of the CPE. Finally, the method includes pushing,to the CPE, the COS template unique to the job assignment matching theidentity of the CPE, to configure the CPE for performing the intendedoperation.

Particular embodiments may comprise one or more of the followingfeatures. The CPE may belong to a device family. The FQDN may be uniqueto the device family. The provisioning of the COS template may includeselecting and populating at least one device profile defined for thedevice family with the service information of the job assignment. CPEsbelonging to the same device family may be configurable using a shareddevice profile. The device family may be one of a CPE manufacturer and aCPE model. The device family of the CPE may be determined by the ZTPserver using the provisioning request received from the CPE. The devicefamily of the CPE may be determined based on the FQDN through which theZTP server receives the provisioning request. The device family of theCPE may be determined through one of a serial number and a MAC addressreceived in the provisioning request and resolvable to at least thedevice family of the CPE. The CPE may be preconfigured to send theprovisioning request to the FQDN in response to the CPE being pluggedinto a network link at the specific customer premises for a first time.

Aspects and applications of the disclosure presented here are describedbelow in the drawings and detailed description. Unless specificallynoted, it is intended that the words and phrases in the specificationand the claims be given their plain, ordinary, and accustomed meaning tothose of ordinary skill in the applicable arts. The inventors are fullyaware that they can be their own lexicographers if desired. Theinventors expressly elect, as their own lexicographers, to use only theplain and ordinary meaning of terms in the specification and claimsunless they clearly state otherwise and then further, expressly setforth the “special” definition of that term and explain how it differsfrom the plain and ordinary meaning. Absent such clear statements ofintent to apply a “special” definition, it is the inventors' intent anddesire that the simple, plain and ordinary meaning to the terms beapplied to the interpretation of the specification and claims.

The inventors are also aware of the normal precepts of English grammar.Thus, if a noun, term, or phrase is intended to be furthercharacterized, specified, or narrowed in some way, then such noun, term,or phrase will expressly include additional adjectives, descriptiveterms, or other modifiers in accordance with the normal precepts ofEnglish grammar. Absent the use of such adjectives, descriptive terms,or modifiers, it is the intent that such nouns, terms, or phrases begiven their plain, and ordinary English meaning to those skilled in theapplicable arts as set forth above.

Further, the inventors are fully informed of the standards andapplication of the special provisions of 35 U.S.C. § 112(f). Thus, theuse of the words “function,” “means” or “step” in the DetailedDescription or Description of the Drawings or claims is not intended tosomehow indicate a desire to invoke the special provisions of 35 U.S.C.§ 112(f), to define the invention. To the contrary, if the provisions of35 U.S.C. § 112(f) are sought to be invoked to define the inventions,the claims will specifically and expressly state the exact phrases“means for” or “step for”, and will also recite the word “function”(i.e., will state “means for performing the function of [insertfunction]”), without also reciting in such phrases any structure,material or act in support of the function. Thus, even when the claimsrecite a “means for performing the function of . . . ” or “step forperforming the function of . . . ,” if the claims also recite anystructure, material or acts in support of that means or step, or thatperform the recited function, then it is the clear intention of theinventors not to invoke the provisions of 35 U.S.C. § 112(f). Moreover,even if the provisions of 35 U.S.C. § 112(f) are invoked to define theclaimed aspects, it is intended that these aspects not be limited onlyto the specific structure, material or acts that are described in thepreferred embodiments, but in addition, include any and all structures,materials or acts that perform the claimed function as described inalternative embodiments or forms of the disclosure, or that are wellknown present or later-developed, equivalent structures, material oracts for performing the claimed function.

The foregoing and other aspects, features, and advantages will beapparent to those artisans of ordinary skill in the art from theDESCRIPTION and DRAWINGS, and from the CLAIMS.

BRIEF DESCRIPTION OF THE DRAWINGS

The disclosure will hereinafter be described in conjunction with theappended drawings, where like designations denote like elements, and:

FIG. 1 depicts a high-level block diagram of a system according to oneembodiment;

FIGS. 2 and 3 depict a flow diagrams of methods according to variousembodiments;

FIG. 4 depicts a high-level block diagram of a computer suitable for usein performing the functions described herein;

FIG. 5 is a schematic view of an agnostic zero touch provisioning (ZTP)system; and

FIG. 6 is a flow view of an agnostic zero touch provisioning method in aZTP system.

DETAILED DESCRIPTION

This disclosure, its aspects and implementations, are not limited to thespecific material types, components, methods, or other examplesdisclosed herein. Many additional material types, components, methods,and procedures known in the art are contemplated for use with particularimplementations from this disclosure. Accordingly, for example, althoughparticular implementations are disclosed, such implementations andimplementing components may comprise any components, models, types,materials, versions, quantities, and/or the like as is known in the artfor such systems and implementing components, consistent with theintended operation.

The word “exemplary,” “example,” or various forms thereof are usedherein to mean serving as an example, instance, or illustration. Anyaspect or design described herein as “exemplary” or as an “example” isnot necessarily to be construed as preferred or advantageous over otheraspects or designs. Furthermore, examples are provided solely forpurposes of clarity and understanding and are not meant to limit orrestrict the disclosed subject matter or relevant portions of thisdisclosure in any manner. It is to be appreciated that a myriad ofadditional or alternate examples of varying scope could have beenpresented, but have been omitted for purposes of brevity.

While this disclosure includes a number of embodiments in many differentforms, there is shown in the drawings and will herein be described indetail particular embodiments with the understanding that the presentdisclosure is to be considered as an exemplification of the principlesof the disclosed methods and systems, and is not intended to limit thebroad aspect of the disclosed concepts to the embodiments illustrated.

According to various embodiments described herein, methods, apparatusand software related products (e.g., a computer readable memory or astorage device) are presented for enabling and otherwise providing forthe automatic or “zero touch” provisioning of Customer PremisesEquipment (CPE). While the invention will be primarily described withinthe context of automatic provisioning of CPE within a MVPD deliverynetwork, it will be appreciated by those skilled in the art that theteachings of the various embodiments are also applicable to otherbroadband services delivery networks.

FIG. 1 is a block diagram of a simplified system useful in illustratingthe provisioning of Customer Premises Equipment (CPE) according tovarious embodiments. That is, FIG. 1 depicts a simplified block diagramof a broadband services delivery network benefiting from the variousembodiments. Specifically, the broadband services delivery network 100of FIG. 1 as depicted comprises a MVPD distribution/delivery network,though other types of distribution/delivery networks may benefit fromthe various embodiments.

The broadband services delivery network 100 comprises, illustratively, ahead end 110 adapted to communicate with a provisioning manager orserver 115, an authentication manager or server 120 and a plurality ofprovider edge routers 130-1 through 130-N (collectively provider edgerouters 130).

The head end 110 may comprise a cable television head end or networkserver operative to provide broadband services to subscribers/customers,manage subscriber/customer sessions, propagate content towardsubscribers/customers, interact with subscriber/customer CPE and thelike. The head end 110 may also provide various session managementfunctions associated with the services instantiated by or on behalf ofvarious subscribers or customers of the service provider. Sessionmanagement functions generally include sending data to CPE such ascommands, encryption keys and the like, receiving data from CPE such asinformation stream requests, session initiation data (set-topidentification, authorization information etc.), user interactioninformation and the like.

Each of the edge routers 130 is adapted to communicate with a respectivegroup of subscribers/customers via respective CPE located at thesubscriber/customer house, office or other location. Subscriber/customerCPE may comprise, illustratively, modems or network interface devices140, set top boxes (STBs) 150 and other types of CPE such as wirelessaccess points (WAPs) and the like as will be appreciated by thoseskilled in the art. Further, various user devices 155 may communicatewith the service provider network via the CPE, such as wireless orwireline routers (not shown) connected via the modem 140, mobile devicesconnected via a wireless access point (WAP) in communication with themodem 140 and so on.

FIG. 1 also depicts an illustrative customer location such as a house orbusiness address having a Network Interface Device (NID) or modemcommunicating with provider network via edge node 130-2, andcommunicating with CPE 150. CPE 150 is depicted as comprising computingapparatus including one or more processors 153, memory 154 andinput/output circuitry 156. The memory is further depicted as includinga pre-configuration script 154-PCS, a gold configuration script 154-GCS,and other programming 154-OTH.

The pre-configuration script 154-PCS may be stored in memory 154 at timeof CPE manufacturer, or received from local modem 140 in response topowering on CPE 150 for the first time while connected to local modem140. Generally speaking, the pre-configuration script 154-PCS is invokedat initial power up (or CPE refresh) to provide thereby defaultinformation such as enabling the CPE to automatically interact with aremote Zero Touch Provisioning (ZTP) entity (e.g., provisioning manageror server 115) to request CPE configuration and service provisioninginformation therefrom, such as by automatically transmitting CPEidentification information to one or more stored ZTP server addresses.The gold-configuration script 154-GCS comprises CPE configuration andservice provisioning information received from the ZTP entity, such asprovided by a class of service (COS) template specifically designed toprovision the CPE 150 in accordance with the premises-specificenvironment of the network and the customer specific services to beprovided via the network 100. The various scripts and other programmingwill be described more detail below.

Referring to FIG. 1, provider edge router 130-2 is depicted ascommunicating with a group of network interface devices (NIDs) 140-1through 140-N (collectively network interface devices 140). However, invarious embodiments where the NID 140 is not necessary to connect thenode 130 and subscriber/customer CPE, the node 130 andsubscriber/customer CPE is connected directly to the communicationsnetwork via some other link or interface mechanism.

The authentication manager or server 120 comprises a management entityadapted to implement various CPE authorization mechanisms to ensure thatCPE accessing the provider network are authorized to do so. Theauthentication manager 120 may be implemented as a standalone entityinteracting with CPE via the head end 110, via the edge router 130 orvia some other network entity in direct or indirect communication withCPE to be authorized. In various embodiments, the authentication manager120 is included as a module or element within the head end 110 and/oredge router 130. The authentication manager 120 may be implementedwithin, or interact with, one or more of the edge router 130 to providea CPE authorization mechanism for respective groups ofsubscribers/customers.

The provisioning manager 115 comprises a management entity adapted toimplement various CPE provisioning mechanisms to ensure that newlyinstalled, updated or refreshed CPE, as well as any other networkelements supporting CPE access to the network and network services, areappropriately provisioned to enable CPE access to the provider networkand to the relevant services associated with the CPE. Various operationsassociated with the provisioning manager 115 will be described in moredetail below with respect to FIGS. 2-3.

The provisioning manager 115 may be implemented as a standalone entityor server interacting with CPE via the head end 110, via the edge router130 or via some other network entity in direct or indirect communicationwith a CPE to be provisioned. In various embodiments, the provisioningmanager 115 is included as a module or element within the head end 110and/or edge router 130. The provisioning manager 115 may be implementedwithin, or interact with, one or more of the edge router 130 to providea CPE provisioning mechanism for respective groups ofsubscriber/customer CPE. In the context of the present description, thisautomated CPE provisioning mechanism may be referred to as Zero TouchProvisioning (ZTP) because, according to various embodiments, fieldinstallation/service personnel are typically not needed to install CPEat customer locations. Accordingly, the provisioning manager 115 mayalso be referred to as a provisioning server 115 or a ZTP server 115, inthe various embodiments disclosed below.

Zero touch provisioning of CPE provides a number of advantages overtraditional methods and procedures for installing new CPE at a customerlocation, or reconfiguring CPE already present at the location.Traditionally, such an installation may require the time and cost ofhaving one or more service provider technicians, and possibly also oneor more technicians from the hardware vendor, who manually connect tothe CPE to tie into the service provider's network and establish contactwith a network operations center, who can push down equipmentconfigurations. This can be a slow and expensive process.

Advantageously, the use of the ZTP systems and methods contemplatedherein allow such an installation to be performed by the customer ortheir agents, often by simply plugging in a new CPE device that wasshipped to the customer location, or configuring a CPE to contact a FQDNprovided by the service provider. ZTP configuration of the CPE is bothfaster and less expensive than conventional methods, which may benefitboth the customer as well as allow smaller service providers to competewith the larger, well established corporations. This leveling of theplaying field may facilitate disruptive innovation within an industrythat has been dominated by a few large corporations who sometimes profitmore from maintaining the status quo.

It is noted that the various elements described herein with respect tothe service provider entities as well as customer entities may beimplemented using computing apparatus such as described below withrespect to FIG. 4. That is, the various elements such as the head end110, authentication manager 120, provisioning manager 115, edge routers130, network interface devices or modems 140, and/or customer premisesequipment 150 may be implemented in whole or in part using computingapparatus such as described below with respect to FIG. 4, and as knownin the art.

Generally speaking, CPE provisioning comprises configuring the CPEitself as well as configuring various services, protocols, function andthe like as needed to support the services to be used by the CPE. Theseservices and service attributes may include, but are not limited to, aDynamic Host Configuration Protocol (DHCP) pool of addresses that theCPE should use, particular public and/or private Internet Protocol (IP)address(es) to be used by the CPE, a Virtual Local Area Network (VLAN)to which the CPE should belong, the Quality of Service (QoS) parametersassociated with the relevant services, a Virtual Private Network (VPN),Transmission system 1 (T1) data, Primary Rate Interface (PRI) data,Multiprotocol Label Switching (MPLS), SIP trunking, SIP proxy serverrequests, and the like. These parameters must be configured inaccordance with the customer's specific network environment.

Further, after initial authentication of CPE to the provider network,additional provisioning steps may be required. For example, in someembodiments, identifying the CPE Media Access Control (MAC) address mayoccur after the initial authentication. In other embodiments,identifying the CPE MAC address may be performed before the CPE is fullyauthenticated, as will be discussed in greater detail with respect toFIGS. 5 and 6, below. Various embodiments contemplate authentication ofthe CPE after provisioning of the CPE 150 via the ZTP server 115.

Various embodiments contemplate providing to each CPE to be configured apre-configured script as part of a CPE discovery agent instantiatedwithin the CPE when powered up. The pre-configured script may comprise astandard of “gold” script included within the CPE during manufacture orincluded within the CPE prior to sending the CPE to a customer locationfor installation.

Various embodiments contemplate that CPE 150 such as a router includesan Ethernet interface and a preconfiguration script 154-PCS with DHCP IPenabled so that the CPE 150 calls out for a dynamic IP address via themodem 150 (e.g., CPE 150 connected to MTA Ethernet output of modem 140)when first plugged in.

Various embodiments contemplate providing to each CPE to be configured arespective configuration template as part of a CPE-deployed agentinstantiated within the CPE after power up, such as after an initialdiscovery process has been performed (e.g., according to the discoveryagent pre-configuration script, etc.). The respective configurationtemplate, in some embodiments referred to as a class of service (COS)template, may be sent by the provisioning manager 115 to the CPE 150 asa file using file transfer protocol (ftp), as a network message or viasome other format or delivery mechanism (e.g. HTTP, HTTPS, etc.).

Various provider equipment or entities cooperate to implement the CPEprovisioning mechanisms of the various embodiments. For example, in oneembodiment the following entities perform the following functions toimplement thereby a system or mechanism for receiving and distributingto CPE templates that configure/provision the CPE in an appropriatemanner. In this example, it is assumed that CPE is to be delivered to acustomer's location where the customer will simply connect the power andnetwork cables and power up the modem and CPE, which will then beconfigured and provisioned automatically.

FIG. 2 depicts a method 200 for staging and deploying class of service(COS) templates suitable for use in a ZTP server, such as theprovisioning manager 115 discussed above with respect to FIG. 1.

At step 210, the ZTP server 115 receives a customer specification ofnetwork requirements (CSNR) defined exclusively for the customerpremises equipment (CPE) associated with a predefined customer. Forexample, a CSNR may be specified for a CPE device to be delivered to acustomer home or business, such as a set-top box (STB), a CPE router, aCPE switch, a voice over Internet protocol (VoIP) device or other CPEdevice. The location of the customer home or business (i.e., thecustomer location) is known, the network topology associated with theneighborhood is known, the initial services to be provided to thecustomer is known. According to various embodiments, the CSNR mayspecify the customer location (e.g. public IP address, mailing address,coordinates, etc.), network topology, initial services to be provided tothe customer, and the like. In some embodiments, a CSNR may specify allof the services to be provided to the customer at the customer location,possibly requiring the provisioning of multiple CPE. In otherembodiments, a CSNR may be defined for each CPE to be provisioned.

At step 220, the ZTP server provisions a class of service (COS) templatedefined exclusively for a CPE associated with the predefined customer,where the COS template defines the operation of the CPE and is based atleast on the CSNR. In various embodiments, the class of service (COS)template comprises service configuration layer information, such asinformation indicating at least one of voice quality and a voice sessioninitiation protocol (SIP) trunking.

At step 230, the ZTP server stores the COS template and identifyinginformation associated with the CPE as a job assignment. In variousembodiments, the job assignment comprises one of a plurality of jobassignment entries in a table of job assignments for a correspondingplurality of CPEs. The table may be stored in the ZTP server or someother management entity.

At step 240, the ZTP server receives from the CPE a provisioning requestsignal including the identity of the CPE upon the CPE being plugged intoa network link at the customer premises for the first time. In variousother embodiments, the CPE signal including the identity of the CPE maybe transmitted by the CPE in response to a remotely generated refreshsignal, a locally generated refresh signal and the like.

In various embodiments, the identity of the CPE is based upon amanufacturer serial number or other serial number associated with theCPE. In various embodiments, the ZTP server is identified by an autolink within the CPE upon CPE power up the first time (or refresh). Theauto link may comprise a fully qualified domain name (FQDN) associatedwith the ZTP server or some other resource locator or identifier. Invarious embodiments, the CPE may be identified via a Media AccessControl (MAC) address.

In various embodiments, a communication path between the ZTP server andthe CPE includes a modem or network link installed in the customerpremises at configured to communicate with an access network of theservice provider.

At step 250, based at least on the received CPE identity informationmatching a stored job assignment, the ZTP server transmits toward therespective CPE service information including at least the COS templateinformation associated with the stored job assignment.

In various embodiments, the COS template information is not transmittedtoward the respective CPE until the respective CPE is authenticated.Examples of service attribute information transmitted toward the CPEinclude, but are not limited to, point-to-point protocol (PPP)information, local area network (LAN) information, Quality of Service(QoS) information, Dynamic Host Configuration Protocol (DHCP)information, Virtual Local Area Network (VLAN) information, VirtualPrivate Network (VPN) information, Transmission System 1 (T1)information, Primary Rate Interface (PRI) information, MultiprotocolLabel Switching (MPLS) information, SIP trunking, SIP proxy serverrequests, firewall Access Control Lists (ACL), and the like.

FIG. 3 depicts a method 300 for zero touch provisioning invoked at a CPEto retrieve and implement configuration and service information such asprovided via a COS template requested by the CPE and received from theZTP upon CPE initial power up or refresh.

At step 310, in response to initial power up or a refresh command, theCPE invokes a configuration template stored within the CPE andcomprising an auto link to a ZTP server in a network. According tovarious embodiments, the auto link points to a FQDN that resolves to theZTP server. In various embodiments, the configuration template isincluded within the CPE by the manufacturer of the CPE. In variousembodiments, the configuration template is communicated to the CPE by amodem or other device associated with the service provider and local tothe CPE. That is, the CPE may receive an initial configuration templateor a replacement configuration template from a modem at the customerlocation.

At step 320, in response to detecting the presence of a communicationnetwork link, the CPE authenticates itself to the network, if necessary.For example, if the CPE is connected and powered on for the first timeat a customer location, prior to receiving network services above theminimum necessary to provide authentication, the CPE must beauthenticated as authorized for receiving such network services.Generally speaking, the CPE will communicate identification informationsuch as an identification number (e.g. manufacturer serial number,etc.), MAC address, and the like, to an authentication manager such asauthentication manager 120. If the authentication manager determinesthat the CPE is authorized to access network services, then theauthentication manager will communicate suchauthorization/authentication to other management entities such as headend 110, provisioning manager 115, and the like.

Various embodiments contemplate authentication of the CPE after theprovisioning of the CPE via the ZTP server. In these embodiments, thefunctions of step 320 may instead be performed after some or all of thefollowing steps have been completed.

At step 330, in response to detecting the presence of a communicationnetwork link, the CPE transmits a provisioning request signal includingthe identity of the CPE toward a ZTP server associated with an auto linkincluded within the configuration template. The auto link comprises anIP address or Uniform Resource Locator (URL) associated with a ZTPserver. In various embodiments, the auto link to the ZTP servercomprises a fully qualified domain name (FQDN) of the ZTP server or, insome embodiments, a hostname or account through a FQDN service thatresolves to a customer or hardware specific aspect of the ZTP server.

In various embodiments, the communication network link between thecommunication network and the CPE may be provided in any standard mannersuch as via a coaxial cable, a twisted pair, an optical fiber a networkcable (e.g., ETHERNET), and the like. The communication network link maybe directly connected to the communication network, or connected via amodem at the customer location.

At step 340, the CPE waits to receive service information including atleast a COS template created for the CPE from the ZTP server.Optionally, in various embodiments multiple links to ZTP servers areprovided within the configuration template to enable the CPE to transmita provisioning request signal to one or more other ZTP servers if needed(e.g., initial or subsequent ZTP server does not respond within apredefined time period). That is, in various embodiments step 330 may berepeated as necessary if an initial or subsequent ZTP server is notreachable by the CPE.

At step 350, upon receiving the service information including at least aCOS template created for the CPE, the CPE performs the variousconfiguration and service provisioning processes indicated by theservice information and COS template such that the CPE is properlyconfigured for operation with the service provider network and properlyconfigured for delivering the appropriate network services to thecustomer.

Thus, the method 300 provides a mechanism which a CPE requests andreceives service information (including at least a COS template) whichwas generated specifically for that customer CPE device in accordancewith a customer specification of network requirements (CSNR). In thismanner, the customer only needs to plug the CPE into the local modem andthe CPE will configure itself and those services appropriate to thecustomer.

In various embodiments, the provisioning manager or server 115 or ZTPserver stages pre-provisioned Class of Service (COS) templates that maybe allocated to assigned CPE serial numbers associated with specificcustomers, or may comprise default COS templates for use in the absenceof customer-specific COS templates. In some embodiments, the staging ofCOS templates is performed prior to the scheduled delivery/installationday associated with the customer CPE, such as hours (same day COStemplate generation/association), days or weeks ahead of CPE delivery tocustomers. In other embodiments, a COS template may be provisioned aftera provisioning request has been sent by a CPE, which will be discussedfurther with respect to FIGS. 5 and 6, below.

Staging comprises determining configuration and provisioning informationassociated with both the local CPE environment and the local CPEcustomer services to be delivered. To do this, the serial number orother unique identifier of the CPE to be delivered to an individualcustomer is identified such that the CPE identifier may be associatedwith that customer through a job assignment. COS templates associatedwith CPE serial numbers are configured to support the various functionsrequired of the CPE when configured to support respective customerrequirements and services.

In various embodiments, the provisioning manager or server 115 considerseach such CPE-to-customer association, as well as the respective COStemplate, to be one job within a batch of jobs assigned. Each job isstored in a claim table or database by the ZTP server.

In some embodiments, a new device claim table is used by the ZTP serverto push an initial or bootstrap configuration to the CPE. The initialconfiguration enables the CPE to find and interact with the ZTP serverupon CPE power up at the customer location. The bootstrap configurationmay be pushed to the CPE at a time of CPE manufacture, at a time oftesting CPEs received from the manufacturer, at a time of testing CPEsprior to deployment or customer delivery, or at an initial CPE power uptime (if stored local and available to the CPE, such as within a modemat the customer premises). The initial configuration provides variousservice attributes such as those for setting up VLAN, PPP, LANData/Voice DHCP, COS, QoS, as well as further complex networkconfigurations as discussed herein.

The CPE plug and play utilizes, in one embodiment, FQDN auto-links andDHCP options pre-written and flashed to CPE configurations tables withwhat is denoted herein as a “Gold Configuration” such as at the pointthat CPE inventory reaches a distributor. This enables prompt handoff ofthe CPE within a warehouse environment for CPE pickup or packageshipments.

At a customer location, after connection of power and network cabling,the CPE is powered up. At this point, the CPE finds home base (e.g., viaFQDN and DHCP-Gateway Options) and, once a live loop is plugged into theCPE Ethernet port, the AG router IP redirector sends traffic destinedfor the service provider's DHCP scope, ZTP domain, hosted within DMZ forsecure DHCP IP assignment and authentication to ZTP Server for push ofbootstrap template configuration.

Authentication may be performed before or after CPE configuration viathe configuration file and interaction with the CDP domain. Once IPauthentication of the ZTP agent (CPE/IAD) has initialized through theTransport & AR IP Edge (via VLAN Specific/DMZ tunneling), to DHCP's IPController for IP assignments (Utilizing Options 43 & 60—Vendor SpecificIdentifier); authenticating CPE's entry into the ISP (Internet ServiceProvider) network, where DNS will direct CPE to ZTP Server's—FQDNresidence (ztp-cpe.isp.com). Thus, enabling a secure registration withinour DMZ and ZTP Server's new device claim table, which will then promptfor automatic template push of bootstrap configuration files, firmwareupdates, as well as any further routing tables or protocols required.

The various embodiments described above generally provide a mechanism inwhich a standard router, switch or other CPE may be associated withspecific “golden configuration file” designed to enable that specificCPE to properly configure itself to its intended customer premisesnetwork environment, and properly configure itself to the servicesappropriate to its intended customer.

In various embodiments, a Fully Qualified Domain Name (FQDN) includedwithin a pre-configuration file is used by the CPE wherever it may bedeployed. Based on the FQDN, the Domain Name Server (DNS) knows to pointthe domain name to a specific location. Thus, once the CPE powers up, itknows where it resides within a network. Further, based on the MACaddress of the CPE, the network service provider knows the class ofservices associated with the customer and can push down to the CPE thenecessary configuration information as part of the golden configurationfile.

Advantageously, these various mechanisms enable a company deploying CPEto have the CPE tested remotely up to some demarcation point, such as anEthernet connection that plugs into the CPE. In some embodiments, theremote testing may also detect and facilitate resolution of problems ormisconfigurations downstream from the CPE (e.g. past the Ethernetconnection of the CPE, etc.). If such testing indicates that the CPE isnot functioning or at least not reachable, then a new CPE may be shippedto the customer directly rather than sending a technician todiagnose/repair/replace. The customer merely unplugs the old CPE andreplaces it with the new CPE. The configuration processes describedherein proceed to provision the replacement CPE rapidly and correctly.

Similarly, if the MAC address of an old CPE device to be replaced isknown, then a “snapshot” of the configuration parameters associated withthat CPE device may be captured and used to populate similarconfigurations of a replacement CPE device. This configuration snapshotmay be performed for every CPE device within a system upon successfulprovisioning/configuration of that device. This information may bestored in a database associated with the provisioning manager or server115, head end 110 or some other network entity. Thus, prior to shippingreplacement CPE out to a customer, the configuration associate of theold CPE is staged as described above with respect to FIG. 2 such thatupon the new CPE pairing up, the appropriate configuration informationis provided thereto.

Pre-staging of templates with old images of CPE waiting to be called outby new CPE provides improvements in customer service response timeswhile reducing on-site technician calls. CPE images may comprisepre-provisioning information (e.g., default configuration templates),post-provisioning information (e.g., staged configuration templates orCOS templates), existing MAC addresses, MAC addresses of CPE to beshipped and so on.

In various embodiments, a replacement CPE may be automatically beupdated with configuration and service provisioning informationassociated with a failed CPE at a customer location. For example, in oneembodiment where the MAC address of the new and old CPE is known, thereplacement CPE is provided with the configuration and serviceprovisioning information originally generated for the failed CPE at thecustomer location. Thus, when the replacement CPE is initially poweredon at the customer location, if the ZTP server determines that aprovisioning request is received from a replacement CPE, the ZTP serverwill transmit the same service information to the replacement CPEinitially generated for use by the failed CPE.

FIG. 4 depicts a high-level block diagram of a computing device 400suitable for use in performing various functions described herein withrespect to the disclosed embodiments, such for implementing any devicelike device IO as described above with respect to the various figures.FIG. 4 is a simplified block diagram of a computing/electronic devicethat is suitable for practicing the exemplary embodiments of thisinvention, and a specific manner in which components of the device areconfigured to cause that device to operate.

As depicted in FIG. 4, computer (computing device) 400 includes aprocessor element 403 (e.g., a central processing unit (CPU) and/orother suitable processor(s)), a memory 404 (e.g., random access memory(RAM), read only memory (ROM), and the like), a cooperatingmodule/process 405, and various input/output devices 406 (e.g., a userinput device (such as a keyboard, a keypad, a mouse, and the like), auser output device (such as a display, a speaker, and the like), aninput port, an output port, a receiver, a transmitter, and storagedevices (e.g., a solid state drive, a hard disk drive, an optical driveand the like).

It will be appreciated that the functions depicted and described hereinmay be implemented in hardware and/or in a combination of software andhardware, e.g., using a general purpose computer, one or moreapplication specific integrated circuits (ASIC), and/or any otherhardware equivalents. In one embodiment, the cooperating process 405 canbe loaded into memory 404 and executed by processor 402 to implement thefunctions as discussed herein. Thus, cooperating process 405 (includingassociated data structures) can be stored on a computer readable storagemedium, e.g., RAM memory, magnetic or optical drive or diskette, and thelike.

It will be appreciated that computing device 400 depicted in FIG. 4provides a general architecture and functionality suitable forimplementing functional elements described herein or portions of thefunctional elements described herein.

It is contemplated that some of the steps discussed herein may beimplemented within hardware, for example, as circuitry that cooperateswith the processor to perform various method steps. Portions of thefunctions/elements described herein may be implemented as a computerprogram product wherein computer instructions, when processed by acomputing device, adapt the operation of the computing device, such thatthe methods and/or techniques described herein are invoked or otherwiseprovided. Instructions for invoking the inventive methods may be storedin tangible and non-transitory computer readable medium such as fixed orremovable media or memory, and/or stored within a memory within acomputing device operating according to the instructions.

As discussed above, conventional methods for provisioning CPE units areoften expensive and slow. In a scenario that may be preferable for anetwork service provider, a customer may be requesting the provisioningof new services using new CPE units sourced from the network serviceprovider. The network service provider will have a preferred set ofequipment that their field technicians and back office personnel areadept at installing and configuring. However, even in such a scenario,the customer must wait for, and pay for, one or more field techniciansto be on-site to begin a multi-step provisioning process for each CPEunit.

As a specific example of the conventional provisioning method, a fieldtechnician plugs into the CPE unit, opens a console, and prepares theCPE to make contact and receive instructions. This preparation mayinclude enabling interfaces and hardcoding a particular IP assigned tothe CPE within the customer's network. The technician then makes contactwith a “test and turn up” team, or a network operations center (NOC), tolet them know that device is ready for configuration. In some cases,this process may be repeated for each CPE unit. It is not uncommon for acustomer's intended operation to require numerous CPEs. Even an idealprovisioning scenario, with a customer ordering all new CPE units thatare well understood by the service provider's install team, can be slowand expensive using traditional methods.

However, in many cases, the circumstances of provisioning new ormodified network services are less than ideal for the network serviceprovider and the customer. For example, customers may have alreadyinvested in a collection of CPE units, and do not want the expense ofreplacing all of those units with hardware that is preferred by a newservice provider. As a consequence, sometimes the service provider'sfield technicians are tasked with provisioning CPE units that they areunfamiliar with, requiring the assistance of technicians from theoriginal CPE vendor, further increasing cost and the length of theinstall. There is a wide range of CPE equipment available, providing awide range of capabilities and having a wide range of provisioningprocedures and limitations.

Contemplated herein is a system and method for agnostic zero touchprovisioning of CPE units. These systems and methods are almostidentical to those discussed above, and in many cases operate in exactlythe same way. However, according to various embodiments, an agnostic ZTPsystem is able to automatically provision CPEs from a wide range ofhardware manufacturers, having different provisioning procedures andconfiguration formats. The system does this by identifying a devicefamily that the CPE unit belongs to, and then stages the COS template bypopulating a device profile specific to that device family, using dataderived from the CSNR. The system is effectively agnostic to whathardware is being configured; so long as the information needed toprovision the desired services and an appropriate device profile areknown, the ZTP server can get the CPE up and running at the customerlocation without requiring human intervention, according to variousembodiments.

The agnostic nature of the systems and methods contemplated hereinadvantageously allows a service provider to work with a preferred set ofhardware as well as any other hardware (e.g. CPE units already owned bythe customer, etc.) at roughly the same expense, in both time andresources. The agnostic ZTP system is also adept at being quicklyconfigured to work with a new set of hardware, as it only requires thedefinition of one or more device profiles. Once the device profiles havebeen defined, they can be used over and over to provision CPEs formultiple customers at multiple locations.

FIG. 5 is a schematic view of a non-limiting example of an agnostic zerotouch provisioning (ZTP) system 500. It should be noted that FIG. 5shows the system 500 comprising a ZTP server 501 seemingly isolated, incontrast to the exemplary system shown in FIG. 1, where the orprovisioning manager 115 (or ZTP server 115) is communicatively coupledto a head end 110 and an authentication manager 120. The head end 110,authentication manager 120, and other elements shown in the non-limitingexample of a ZTP system in FIG. 1 have been omitted from FIG. 5, forclarity. In some embodiments, the ZTP server 501 shown in FIG. 5 may beimplemented in an environment similar or identical to the environmentshown in FIG. 1 and discussed above.

In other embodiments, the ZTP server 501 may be implemented separately.For example, in one embodiment, the ZTP server 501 may be added to apreexisting system, such as a CPE management system that a networkservice provider has invested in and made use of. In such an embodiment,the ZTP server 501 may be used for the initial provisioning of the CPEs(e.g. CPEs configured to contact FQDN that leads directly to the ZTPserver 501, etc.), and said provisioning will include any configurationnecessary to ensure the provisioned CPEs look to the legacy managementsystem for future instruction. In other embodiments, the ZTP server 501may also comprise a management functionality that may be used to provideadditional instructions or push out new profiles to CPE units that havealready been provisioned by the system. In still other embodiments, theZTP server 501 may embody some or all of the functionality provided byother elements such as the head end 110 and/or authentication manager120, as discussed above with respect to the provisioning manager 115.

As shown, the ZTP server 501 comprises a processor 403 and a memory 404.It should be noted that the configuration manager 115 discussed above isable to accomplish the same tasks as the ZTP server 501, according tovarious embodiments. The difference between these two embodiments of azero touch provisioning server is that the ZTP server 501 discussedbelow is able to deal with various CPE units having differentproprietary methods of configuration (e.g. file formats, requiredinformation, procedures, etc.) with less effort on the part of thenetwork service provider, or whatever entity is doing the provisioning.

According to various embodiments, the ZTP server 501 is able to dealwith a heterogeneous collection of CPE units using an integration layer.The integration layer is responsible for the collection of a pluralityof device profiles that may be used for configuring various CPE 150units. In the context of the present description and the claims thatfollow, a device profile is a framework that defines a format forconfiguration instructions for a particular service or intended use fora particular family of CPE hardware. Device families and device profileswill be discussed in greater detail, below.

In some embodiments, the integration layer gathers and organizes aplurality of device profiles. In other embodiments, the integrationlayer may also create device profiles, by extrapolating the structure ofa configuration template from provided examples, include open sourceexamples.

Device profiles are defined for device families. In the context of thepresent description and the claims that follow, a device family is acollection of CPE units 150 that are able to receive and executeconfiguration instructions having the same format. In other words, if itis known how to format a configuration script of COS template for onemember of a device family 503, then it is known how to do so for everymember of that device family 503. Every CPE 150 belongs to at least onedevice family 503. As shown, the non-limiting example of a customerpremises 512 of FIG. 5 makes use of three CPE units 150, two belongingto one device family 503, and the other belonging to a different devicefamily 503. It should be noted that device family 503 is only dictatedby the procedures and formats involved with the configuration of thehardware; although the three CPE 150 shown in FIG. 5 belong to twodifferent device families 503, they are not necessarily incompatibleafter being provisioned for their intended usage.

In some embodiments, device family 503 may be defined in terms of themake and model of a CPE 150. For example, many CPE manufacturers havedeveloped proprietary methods and formats for configuring their CPEhardware which may vary from maker to maker. Additionally, over timeconfiguration methods evolve and improve, so additional distinctions maybe drawn between models or product lines. In other embodiments, devicefamilies 503 may be defined in some other way that goes beyond theboundaries of make and model. For example, in one embodiment, one devicefamily 503 may be composed of CPE units 150 that are all compatible witha standardized or open source format for a configuration file.

According to various embodiments, a plurality of device profiles may bedefined before the ZTP server 501 provisions any CPE 150. Over time,more device profiles may be added to the ZTP server 501, to expand itsability to provision CPE units 150.

As shown, the ZTP server 501 is communicatively coupled to a storage502. In some embodiments, the storage 502 may be external to, andcommunicatively coupled with, the ZTP server 501. In other embodiments,the storage 502 may be incorporated into the server 501, and in stillother embodiments, the storage 501 may be remote to the server 501, andcoupled over the network 505 (e.g. cloud storage, etc.). In someembodiments, the storage 502 may be a database, while in otherembodiments the storage 502 may be a file system. Those skilled in theart will recognize that the systems and methods contemplated herein maybe adapted to any of the numerous digital storage technologies andmethods available, now and in the future.

According to various embodiments, the storage 502 may be used to storejobs, COS templates, CSNR, device profiles, and the like. It should benoted that much, if not all, of that information could be stored in textfiles. In some embodiments, each of those data objects may be a separatefile, while in other embodiments, some those data objects may becombined into a single file. In the context of the present descriptionand the claims that follow, each of those data objects will be assumedto hold information for at least one customer, CPE device, location,and/or service, but the inclusion of multiple subjects is not precluded.

In some embodiments, the storage 502 may be structured to represent thedifferent device families 503. For example, in one embodiment making useof a file system, the device profiles may be stored in a directorystructure that branches from manufacturer to model or product line. As aspecific example, in one embodiment, the device profiles for a CPE,model 5600, made by Sequoia, may be stored along a path“dir/sequoia/device-profile/model5600”. Within that directory may be acollection of device profiles that can be used by a Sequoia model 5600CPE (once the device profile is populated) to provision any number ofservices. Of course, in other embodiments, a similar branching structuremay be implemented in a database environment.

In some embodiments, device families 503 may be delineated based onshared instruction sets and functionalities. Of course, in all cases, adevice family 503 is defined by the ability to share configurationmethods and formats. But while some embodiments may store deviceprofiles in terms of manufacturer and model, for example, others maystore the device profiles using an organization based on othercommonalities.

According to various embodiments, device profiles may be provided byhardware manufactures, open source projects, and the like. In somecases, the device profiles may be reverse engineered from proprietaryconfiguration scripts and data structures that otherwise would not beavailable.

In some embodiments, a single device profile may comprise aconfiguration template for provisioning multiple services for a devicefamily 503. In other embodiments, a separate device profile may bedefined for each service that could be provisioned. In some of theseembodiments, a job entry could contain the information specific to acustomer and location, and simply point to the device profile for theappropriate device family and desired service(s). The population ofdevice profiles will be discussed in greater detail with respect to FIG.6, below.

In some embodiments, COS templates may be staged/provisioned and storedbefore a provisioning request is received. These COS templates, whichare specific for a certain customer and location, may be stored usingthe same organization as is used for the device profiles. In otherembodiments, the COS templates may be stored in a different manner.

As shown, one or more CPE 150 may be associated with (e.g. owned by,used by, provided by, paid for by, etc.) a specific customer 510, foruse at a specific customer premises 512, as discussed above. As shown,each CPE 150 belongs to a device family 503, and comprises an identity504 that is unique to each CPE 150. Examples of CPE identities 504include, but are not limited to, serial numbers, MAC addresses, and thelike. In some embodiments, the identity 504 of the CPE 150, which issent as part of a provisioning request (as discussed above), may be usedto determine the device family 503 of the CPE 150.

As mentioned above, the ZTP server 501 may be used to provision CPEs 150provided to the customer 510, as well as CPEs 150 already owned by thecustomer 510, according to various embodiments. CPEs 150 provided by thenetwork service provider have the advantage of having a known identity504, and may be preconfigured for provisioning, as discussed above. Forexample, a CPE 150 may be pre-flashed to have a preconfiguration scriptthat will implement DHCP, obtain an IP address, and send a provisioningrequest to a FQDN pointing to the ZTP server 501 in response to beingplugged into the network link 140 at the customer premises 512 for thefirst time. If the CPE 150 is already owned by the customer 510, andthey wish for it to be provisioned and managed by a new network serviceprovider, they may have to provide the identity 504 of that CPE 150along with the CSNR. When it is time for provisioning to occur, thecustomer 510, an agent of the customer 510, or some other person (e.g.field technician, etc.) can manually instruct the CPE to send aprovisioning request to an FQDN that resolves to the public IP of theZTP server 501.

As shown, the ZTP server 501 and the CPE 150 being provisioned arecommunicatively coupled through a network 505. According to variousembodiments, the CPE 150 may send its provisioning request to a FQDNprovided by the ZTP server 501 or the network service provider which isresolved by a DNS server 506 to point to a public IP address for the ZTPserver 501, as is known in the art. In some embodiments, the FQDN maypoint to a firewall 508 (or the edge node 130 of FIG. 1) which may thenpass the provisioning request along to a private IP address belonging tothe ZTP server 501, if certain access policies are satisfied (e.g. ACLlist, authentication, CPE identity, etc.).

FIG. 6 is a flow view of a non-limiting example of a hardware-agnosticzero touch provisioning method in a ZTP system. Specifically, FIG. 6 isa non-limiting example of the steps taken by a ZTP server 501 inzero-touch provisioning a single CPE 150 at a customer premises 512.

First, a customer specification of network requirements (CSNR) 600 isreceived by the ZTP server 501. See ‘circle 1’. According to variousembodiments, the CSNR 600 is exclusively specified for a particularcustomer premises equipment (CPE) 150 assigned to a specific customer510 at a specific customer premises 512. As discussed above, the CSNR600 includes information describing the customer premise 512 (e.g.public IP address, mailing address, hostname, etc.) and informationdescribing an intended operation to be provided by the CPE 150 for thecustomer 512. In some embodiments, the ZTP server 501 may receive theCSNR 600 as a file prepared on and sent by another machine. In otherembodiments, the information making up the CSNR 600 may be inputdirectly into the ZTP server 501 though an interface. Examples of suchan interface include, but are not limited to, a web managementinterface, network management software, input pulled directly from ane-commerce server where customers 510 may place orders for specificnetwork functionality, and the like. In some embodiments, the CSNR 600may include an identity 504 of a particular CPE 150 (e.g. a CPE 150already owned by the customer 510 that they wish to have provisioned,etc.).

In some embodiments, a CSNR 600 may specify information and intendedoperations that require multiple CPE's 150 to implement. In otherembodiments, a CSNR 600 may need to be supplied for each CPE 150 that isto be provisioned.

Next, a job assignment 604 is stored by the ZTP server 501. See ‘circle2’. As previously discussed, a job assignment 604 includes an identity504 of a specific CPE 150 as well as service information 608 needed forthe zero-touch provisioning of the intended operation of the CPE 150,based on the CSNR 600. The job assignment 604 serves as a record of thelink between a specific CPE 150 (e.g. a CPE 150 that has been shipped tothe customer 510 at a specific customer premises 512, a CPE 150 alreadyin the customer's possession that the customer has identified in theCSNR 600, etc.) and a customer 510/customer premises 512, according tovarious embodiments.

In some embodiments, the job assignment 604 may comprise the COStemplate 610 that will eventually be pushed to the CPE 150, as discussedabove. In other embodiments, the job assignment 604 may point to analready staged COS template 610 that can be pushed to the CPE unit inresponse to a provisioning request 614. In still other embodiments, thejob assignment may simply point to the device profile that will bepopulated to create a COS template 610. As a specific example, a jobassignment 604 may indicate that customer Doggy Daycare at public IP17.21.8.221 needs a Sequoia model 5600 CPE with serial number 565656provisioned for SIP trunking, and include thepath/dir/sequoia/device-profile/model5600/COS-SIP_trunking, pointing toa device profile for SIP trunking with that type of CPE. The COStemplate 610 may be staged by populating the device profile(s) pointedto by the job assignment 604, according to various embodiments.

In still other embodiments, the job assignment 604 may contain theservice information 608 that will be needed to provision a CPE 150 forthe customers intended operation, but a COS template 610 is not stageduntil the CPE 150 makes first contact and the device family 503 isdetermined. Upon determining the device family 503 of the CPE 150, adevice profile 612 can be used to stage the COS template 610.

As previously discussed, the job assignment 604 includes serviceinformation 608 needed to provision the CPE 150. Examples of serviceinformation 608 include, but are not limited to, service attributes forpoint-to-point protocol (PPP), local area network (LAN) data, a qualityof service (QoS) data, dynamic host configuration protocol (DHCP) data,virtual local area network (VLAN) parameters, virtual private network(VPN) data, transmission system 1 (T1) parameters, primary rateinterface (PRI) data, SIP trunking, SIP proxy server requests, andmultiprotocol label switching (MPLS) structures and data. Otherinformation that may be specified in a job assignment 604 includes, butis not limited to, ACLs, interfaces that need to be enabled, credentials(e.g. usernames and passwords, etc.), specific public and/or IPaddresses for that CPE to use, private network topology, and the like.

Next, a Class of Service (COS) template 610 is staged. See ‘circle 3’.As previously discussed, the COS template 610 is what gets pushed to theCPE 150 so that it can configure itself for its intended use. The COStemplate 610 is exclusively created for provisioning a particular CPE150 to perform certain operations at the specific customer premises 512.In some embodiments, the COS template 610 may be provisioned at roughlythe same time as the job assignment 604, or immediately before or after.In other embodiments, the COS template 610 may be provisioned after theassociated provisioning request 614 has been received from the CPE 150and the device family 503 has been determined, as previously discussed.The COS template 610 is provisioned by populating one or more deviceprofiles 612 using information based on the CSNR 600 and at leastreferenced by the job assignment 604, according to some embodiments.

Next, a provisioning request 614 is sent by the CPE 150 to a fullyqualified domain names (FQDN) 616. See ‘circle 4’. In some cases, theCPE 150 being provisioned was provided by the network service provider,and has been flashed with a preconfiguration script before being shippedfrom the manufacturer or network service provider. The preconfigurationscript, according to various embodiments, causes the CPE 150 to obtainan IP number using DHCP upon being connected to a network link 140 atthe customer premises 512 for the first time, and then sending aprovisioning request 614 containing the identity 504 of the CPE 150, asdiscussed above.

In other cases, the CPE 150 may already belong to the customer 510, andis never in the possession of the network service provider or theiragents. In such cases, the customer 510 may be provided with a FQDN 616and instructions on how to manually send the provisioning request 614 tothe FQDN 616 using the CPE 150. In some embodiments, the customer 510may provide the network service provider with the identity 504 of theirCPE 150, so that a job assignment 604 may be staged before theprovisioning request 614 is sent. In other embodiments, the FQDN 616provided to the customer 510 for that particular CPE 150 may be specificenough that the job may be staged without knowing an intrinsic identitysuch as a serial number or MAC address, and the device family 503 may bedetermined at the time of receiving the provisioning request 614. Incases where only a single CPE 150 is being provisioned for a premises512, for a particular static public IP address, the IP address of theCPE 150 may be sufficient to link the job assignment 604 to the CPE 150.

In some embodiments, the FQDN 616 may be unique to a device family 503.In other embodiments, an FQDN 616 may be unique to a specific device,which may be advantageous in cases where the network service providernever has physical access to the CPE before the provisioning.

A DNS server 506 resolves the FQDN 616 to the public IP 618 of the ZTPserver 501. See ‘circle 5’. The FQDN 616 was previously establishedusing an a-record 602, which the DNS server 506 uses to resolve the IPaddress. In some embodiments, the creation of a-records 602 to establishFQDNs 616 for use in zero touch provisioning may be done manually, butin other embodiments, the FQDNs 616 may be created automatically by theZTP server 401.

The provisioning request 614 moves on to the public IP address 618provided by the DNS server 506. In some embodiments, the IP address 618leads to a firewall 508 or edge server that stands between the ZTPserver 501 and the rest of the internet. As is known in the art, thefirewall may make use of an access list or other authentication methodto determine that this particular CPE 150 is allowed to speak with theZTP server 501. The request 614 is passed on to the private IP addressof the server 501.

Next, the device family 503 of the CPE 504 is determined. See ‘circle6’. The device family 503 needs to be determined at some point in theprovisioning process, in order to know which device profile(s) 612should be used to provision a COS template 610 for the CPE 150. In someembodiments, a FQDN 616 is created for each device family 503 and eachCPE 150 being provisioned is either preconfigured or manually instructedto send a provisioning request 614 to the appropriate FQDN 616. All ofthese FQDN's 616 lead back to the same place: the ZTP server 501.However, the server 501 or the firewall 508 will see which FQDN 616 theprovisioning request 614 was redirected from by the DNS server 506, andthus know the device family 503.

Another method the ZTP server 501 may use to determine which devicefamily 503 a CPE belongs to, based on the provisioning request 614 sentby the CPE 150, is using the identity 504 contained within theprovisioning request 614 and unique to that CPE 150. Many uniqueidentities, such as MAC addresses and sometimes even serial numbers, maybe resolved to, at the very least, a manufacturer, and in some casesthey may be resolved down to a model as well.

Next, the COS template is pushed down to the CPE 150 with the identity504 matching the job assignment 604. See ‘circle 7’. According tovarious embodiments, the COS template 610 is pushed down to the CPE 150.The method of pushing the COS template to the CPE 150 may include, butis not limited to HTTP, HTTPS, FTP, and the like.

Finally, the CPE applies the COS template. See ‘circle 8’. Afterreceiving the COS template 610, the CPE 150 performs the variousconfiguration and service provisioning processes indicated in the COStemplate 610, such that the CPE 150 is properly configured for operationwith the service provider network and properly configured for deliveringthe appropriate network services to the customer 510.

The following is a specific but non-limiting example of a ZTP server 501being used to zero-touch provision a CPE device. A customer wishes toswitch to a different network service provider, and at the same timeexpand the service they are using. Specifically, they wish to establisha PBX system, to function alongside the VLAN already in place. Ratherthan sending a field technician to install the new CPE and reconfigurethe old CPE, requiring the customer to wait for the technician to beavailable and increasing the expense of the transition, the new networkservice provider simply records the details regarding the desiredservices, including the specifics for the VLAN set up on older CPEequipment by another provider. A new CPE is immediately shipped to thecustomer after its serial number is noted in the ZTP server managementsystem, alongside all of the information received from the customer. Thenew CPE device arrives the next day. While the CPE was in transit, thenetwork service provider created a CSNR that details the desired PBXsystem for that customer location, the service information needed, andthe identity (i.e. serial number) of the CPE being sent.

At the same time, the ZTP server provisions a new FQDN that is specificto this new customer, at this location, for their legacy CPE used tocreate a VLAN. Another CSNR is created detailing the VLAN and allassociated service information obtained from the customer. A jobassignment is created for the VLAN, pointing to the new, unique FQDN.Another job assignment is created for the PBX, including the serialnumber of the CPE that is in transit.

When the new CPE device is first plugged into the customers network, itexecutes a script that was flashed onto the CPE memory by themanufacturer. First, it obtains an IP address using DHCP, and then itsends a provisioning request containing its own serial number to an FQDNestablished for that particular type of CPE that the network serviceprovider prefers for creating PBX systems. The FQDN resolves to the IPaddress of the ZTP server. Upon examination of the provisioning request,the server 501 determines that it has a job assignment matching thatserial number. That job assignment is pointing to an already provisionedCOS template stored and waiting. The COS template is sent back to thenew CPE, which executes it and configures itself into the desired PBXsystem.

The customer, following instructions provided by the new network serviceprovider, manually instructs their old CPE to send a provisioningrequest to the FQDN provided by the service provider, that is unique tothat CPE at that location. This FQDN resolves to the ZTP server. Uponseeing that the provisioning request is arriving from that very specificFQDN, the ZTP server identifies the device family that the legacy CPEunit belongs to using a detected MAC address. Upon determining thedevice family, the job assignment is pointed to the appropriate deviceprofile for VLAN implemented with that equipment. A COS template isprovisioned and pushed down to the legacy CPE, which uses the COStemplate to configure itself to be managed and maintained by the newservice provider. All of this happening without needing interventionfrom a field technician, lengthy delays, or additional costs.

Various modifications may be made to the systems, methods, apparatus,mechanisms, techniques and portions thereof described herein withrespect to the various figures, such modifications being contemplated asbeing within the scope of the invention. For example, while a specificorder of steps or arrangement of functional elements is presented in thevarious embodiments described herein, various other orders/arrangementsof steps or functional elements may be utilized within the context ofthe various embodiments. Further, while modifications to embodiments maybe discussed individually, various embodiments may use multiplemodifications contemporaneously or in sequence, compound modificationsand the like.

The various embodiments contemplate an apparatus configured to providefunctions as described herein, such as an apparatus comprising aprocessor and a memory communicatively connected to the processor, theprocessor configured to perform these functions as described above withrespect to the various figures.

In describing alternate embodiments of the apparatus claimed, specificterminology is employed for the sake of clarity. The invention, however,is not intended to be limited to the specific terminology so selected.Thus, it is to be understood that each specific element includes alltechnical equivalents that operate in a similar manner to accomplishsimilar functions.

It is to be understood that the foregoing description is intended toillustrate and not to limit the scope of the invention, which is definedby the scope of the appended claims. Other embodiments are within thescope of the following claims. It is noted that various non-limitingembodiments described herein may be used separately, combined orselectively combined for specific applications.

Further, some of the various features of the above non-limitingembodiments may be used to advantage without the corresponding use ofother described features. The foregoing description should therefore beconsidered as merely illustrative of the principles, teachings andexemplary embodiments of this invention, and not in limitation thereof.

Although various embodiments which incorporate the teachings of thepresent invention have been shown and described in detail herein, thoseskilled in the art can readily devise many other varied embodiments thatstill incorporate these teachings. Thus, while the foregoing is directedto various embodiments of the present invention, other and furtherembodiments of the invention may be devised without departing from thebasic scope thereof. As such, the appropriate scope of the invention isto be determined according to the claims.

The invention claimed is:
 1. A method for zero touch provisioning,performed by a zero touch provisioning (ZTP) server in a network, themethod comprising: receiving a customer specification of networkrequirements (CSNR) exclusively specified for a customer premisesequipment (CPE) belonging to a device family and assigned to a specificcustomer at a specific customer premises, the CSNR received prior to theCPE being plugged into a network link at the specific customer premisesfor a first time and comprising information describing the specificcustomer premises and information describing an intended operation to beprovided by the CPE for the specific customer, the CPE beingpreconfigured to send a provisioning request to a fully qualified domainnames (FQDN) unique to the device family and pointed at an IP address ofthe ZTP server, the provisioning request sent in response to the CPEbeing plugged into the network link at the specific customer premisesfor the first time, wherein CPEs belonging to the same device family areconfigurable using a shared device profile; storing, prior to receivingthe provisioning request from the CPE, a job assignment comprising anidentity that is unique to the CPE and service information for the zerotouch provisioning of the intended operation of the CPE based on theCSNR, the identity being linked to the specific customer through the jobassignment; provisioning a class of service (COS) template by selectingand populating at least one device profile defined for the device familywith the service information of the job assignment, the COS templateexclusively created for providing the intended operation of the CPE atthe specific customer premises and paired with the identity of the CPEthrough at least the job assignment; receiving, from the CPE, theprovisioning request sent by the CPE to the FQDN in response to the CPEbeing plugged into the network link for the first time, the provisioningrequest comprising the identity of the CPE; and pushing, to the CPE, theCOS template provisioned using the job assignment matching the identityof the CPE, to configure the CPE for performing the intended operation;wherein the device family is one of a CPE manufacturer and a CPE model.2. The method of claim 1, wherein the COS template is provisioned afterthe provisioning request is received from the CPE.
 3. The method ofclaim 1, wherein the service information comprises information relatedto service attributes of at least one of a point-to-point protocol(PPP), local area network (LAN) data, a quality of service (QoS),dynamic host configuration protocol (DHCP), virtual local area network(VLAN), virtual private network (VPN) data, transmission system 1 (T1),primary rate interface (PRI) data, SIP trunking, SIP proxy serverrequests, and multiprotocol label switching (MPLS).
 4. A system for zerotouch provisioning comprising: a customer premises equipment (CPE)assigned to a specific customer at a specific customer premises, the CPEbelonging to a device family, the CPE communicatively coupled to anetwork through a network link at the specific customer premises,wherein CPEs belonging to the same device family are configurable usinga shared device profile; and a zero touch provisioning (ZTP) servercomprising a processor and a memory, the ZTP server configured to:receive a customer specification of network requirements (CSNR)exclusively specified for the CPE, the CSNR comprising informationdescribing the specific customer premises and information describing anintended operation to be provided by the CPE for the specific customer;store a job assignment comprising an identity that is unique to the CPEand service information for the zero touch provisioning of the intendedoperation of the CPE based on the CSNR, the identity being linked to thespecific customer through the job assignment; provision a class ofservice (COS) template using information originating from the CSNR byselecting and populating at least one device profile defined for thedevice family with the service information of the job assignment, theCOS template exclusively created for providing the intended operation ofthe CPE at the specific customer premises and paired with the identityof the CPE through at least the job assignment; receive, from the CPE, aprovisioning request sent by the CPE from the network link at thespecific customer premises to a fully qualified domain name (FQDN)unique to the device family and resolving to an IP address of the ZTPserver, the provisioning request comprising the identity of the CPE,wherein the CSNR is received and the job assignment is stored before theprovisioning request is received; and push, to the CPE over the network,the COS template unique to the job assignment matching the identityreceived in the provisioning request, to configure the CPE forperforming the intended operation.
 5. The system of claim 4, wherein thedevice family is one of a CPE manufacturer and a CPE model.
 6. Thesystem of claim 4, wherein the CPE is preconfigured to send theprovisioning request to the FQDN in response to the CPE being pluggedinto the network link at the specific customer premises for a firsttime.
 7. The system of claim 4, the ZTP server further configured todetermine the device family of the CPE using the provisioning requestreceived from the CPE.
 8. The system of claim 7, wherein the ZTP serveris further configured to determine the device family of the CPE byidentifying the FQDN through which the ZTP server receives theprovisioning request.
 9. The system of claim 7, wherein the ZTP serveris further configured to determine the device family of the CPE usingone of a serial number and a MAC address received in the provisioningrequest and resolvable to at least the device family of the CPE.
 10. Thesystem of claim 4, wherein the COS template is provisioned after theprovisioning request is received from the CPE.
 11. The system of claim4, wherein the service information comprises information related toservice attributes of at least one of a point-to-point protocol (PPP),local area network (LAN) data, a quality of service (QoS), dynamic hostconfiguration protocol (DHCP), virtual local area network (VLAN),virtual private network (VPN) data, transmission system 1 (T1), primaryrate interface (PRI) data, SIP trunking, SIP proxy server requests, andmultiprotocol label switching (MPLS).
 12. A method for zero touchprovisioning, performed by a zero touch provisioning (ZTP) server in anetwork, the method comprising: receiving a customer specification ofnetwork requirements (CSNR) exclusively specified for a customerpremises equipment (CPE) assigned to a specific customer at a specificcustomer premises, the CSNR received prior to the receipt of aprovisioning signal from the CPE from a network link at the specificcustomer premises, the CSNR comprising information describing thespecific customer premises and information describing an intendedoperation to be provided by the CPE for the specific customer; storing,prior to receiving the provisioning request from the CPE, a jobassignment comprising an identity that is unique to the CPE and serviceinformation for the zero touch provisioning of the intended operation ofthe CPE based on the CSNR, the identity being linked to the specificcustomer through the job assignment; provisioning a class of service(COS) template using information originating from the CSNR, the COStemplate exclusively created for providing the intended operation of theCPE at the specific customer premises and paired with the identity ofthe CPE through at least the job assignment; receiving, from the CPE,the provisioning request sent by the CPE from the network link at thespecific customer premises to a fully qualified domain names (FQDN)pointed at an IP address of the ZTP server, the provisioning requestcomprising the identity of the CPE; and pushing, to the CPE, the COStemplate unique to the job assignment matching the identity of the CPE,to configure the CPE for performing the intended operation.
 13. Themethod of claim 12: wherein the CPE belongs to a device family; whereinthe FQDN is unique to the device family; wherein the provisioning of theCOS template comprises selecting and populating at least one deviceprofile defined for the device family with the service information ofthe job assignment; and wherein CPEs belonging to the same device familyare configurable using a shared device profile.
 14. The method of claim13, wherein the device family is one of a CPE manufacturer and a CPEmodel.
 15. The method of claim 13, wherein the device family of the CPEis determined by the ZTP server using the provisioning request receivedfrom the CPE.
 16. The method of claim 15, wherein the device family ofthe CPE is determined based on the FQDN through which the ZTP serverreceives the provisioning request.
 17. The method of claim 15, whereinthe device family of the CPE is determined through one of a serialnumber and a MAC address received in the provisioning request andresolvable to at least the device family of the CPE.
 18. The method ofclaim 13, wherein the COS template is provisioned after the provisioningrequest is received from the CPE.
 19. The method of claim 12, whereinthe CPE is preconfigured to send the provisioning request to the FQDN inresponse to the CPE being plugged into a network link at the specificcustomer premises for a first time.
 20. The method of claim 12, whereinthe service information comprises information related to serviceattributes of at least one of a point-to-point protocol (PPP), localarea network (LAN) data, a quality of service (QoS), dynamic hostconfiguration protocol (DHCP), virtual local area network (VLAN),virtual private network (VPN) data, transmission system 1 (T1), primaryrate interface (PRI) data, SIP trunking, SIP proxy server requests, andmultiprotocol label switching (MPLS).